Hydraulic system with electronic identifiers

ABSTRACT

A hose assembly for a hydraulic system is shown. The hose assembly includes a first hose that fluidly couples a pump with a hydraulic actuator using a first port. The first hose includes a first electronic device that provides identification information for the first hose. The hose assembly further includes a second hose that fluidly couples the hydraulic actuator with a reservoir tank using a second port. The second hose includes a second electronic device that provides identification information for the second hose. The hose assembly further includes a controller that receives a first connection signal and a second connection signal. The controller is further configured to determine that the first hose has fluidly coupled using the first port based on the first connection signal and determine that the second hose has fluidly coupled using the second port based on the second connection signal.

BACKGROUND

The present disclosure relates generally to hydraulic systems for heavymachinery. More specifically, the present disclosure relates tomonitoring hydraulic systems for heavy machinery.

SUMMARY

This summary is illustrative only and is not intended to be in any waylimiting. Other aspects, inventive features, and advantages of thedevices or processes described herein will become apparent in thedetailed description set forth herein, taken in conjunction with theaccompanying figures, wherein like reference numerals refer to likeelements.

One implementation of the present disclosure is a hose assembly for ahydraulic system. The hose assembly includes a first hose that fluidlycouples a pump with a hydraulic actuator using a first port. The firsthose includes a first electronic device that provides identificationinformation for the first hose. The hose assembly further includes asecond hose that fluidly couples the hydraulic actuator with a reservoirtank using a second port. The second hose includes a second electronicdevice that provides identification information for the second hose. Thehose assembly further includes a controller that receives a firstconnection signal using the identification information for the firsthose and a second connection signal using the identification informationfor the second hose. The controller is further configured to determinethat the first hose has fluidly coupled using the first port based onthe first connection signal. The controller is further configured todetermine that the second hose has fluidly coupled using the second portbased on the second connection signal.

In some embodiments, the controller is further configured to determine aconnection fault based on at least one of the first connection signaland the second connection signal. The controller is further configuredto determine that the connection fault is based on at least one of thefirst hose fluidly coupling the pump using the second port or the secondhose fluidly coupling the reservoir tank using the first port. In someembodiments, the controller is further configured to adjust internaloperation of the hydraulic manifold to fluidly couple the pump with thehydraulic actuator using the first hose and to fluidly couple thehydraulic actuator with the reservoir tank using the second hose.

In some embodiments, the hose assembly further includes a hydraulicmanifold, the hydraulic manifold including the first port and the secondport; or the hydraulic actuator including the first port and the secondport. In some embodiments, wherein the first port is configured to allowfluid to flow from the pump to the hydraulic actuator. In someembodiment's, the second port is configured to allow the fluid to flowfrom the hydraulic actuator to the reservoir tank.

In some embodiments, the hose assembly further includes a firsttransmitter proximate to the first port, the first transmitterconfigured to communicate with the first electronic device to receivethe identification information for the first hose. The first transmitterfurther configured to provide the first connection signal based on theidentification information for the first hose. In some embodiments, thefirst connection signal includes an indication that the first hose isconnected to the first port. The hose assembly further includes a secondtransmitter proximate to the second port, the second transmitterconfigured to communicate with the second electronic device to determinethe identification information for the second hose. The secondtransmitter further configured to provide the second connection signalbased on the identification information for the second hose, wherein thesecond connection signal comprises an indication that the second hose isconnected to the second port.

In some embodiments, the first transmitter and the first electronicdevice communicate via passive tag radio-frequency identification(RFID), active tag RFID, near-field communication (NFC), near-fieldmagnetic induction (NFMI), Bluetooth, or Wi-Fi.

In some embodiments, the first electronic device is a passive RFID tagand the first transmitter includes an active RFID reader configured toread the passive RFID tag to determine the identification informationfor the first hose.

In some embodiments, the controller is further configured to provide anotification of the connection fault to a monitoring device of thehydraulic system.

Another implementation of the present disclosure is a method ofdetermining faults in a hydraulic system. The method includes receivingidentification information and connection information for a first hosebased on a first receiver on the first hose, the first hose configuredto fluidly couple a pump with a hydraulic actuator using a first port.The method further includes receiving identification information andconnection information for a second hose based on a second receiver onthe second hose, the second hose configured to fluidly couple thehydraulic actuator with a reservoir tank using a second port. The methodfurther includes determining a connection fault based on at least one ofthe identification information and connection information for the firsthose and the identification information and connection information forthe second hose. The method further includes providing a notification ofthe connection fault to a monitoring device of the hydraulic system.

In some embodiments, receiving identification information and connectioninformation for the first hose includes receiving identificationinformation that identifies a type, a manufacture, a functionality, or aconfiguration of the first hose. The method further includes receivingconnection information that identifies a port that the first hose usesto fluidly couple the pump.

In some embodiments, providing the notification of the connection faultto the monitoring device includes displaying an alert on a userinterface indicating that the connection fault has been detected. Themethod further includes providing a proposed solution to the userinterface, the proposed solution including instructions to reconnect thefirst hose or the second hose to another port or adjust internaloperation of a hydraulic manifold.

In some embodiments, the method further includes determining that thefirst hose is fluidly coupling the pump using the second port and thatthe second hose is fluidly coupling the reservoir tank using the firstport. The method further includes adjusting internal operation of ahydraulic manifold to fluidly couple the pump with the hydraulicactuator using the first hose and to fluidly couple the hydraulicactuator with the reservoir tank using the second hose.

In some embodiments, the hydraulic manifold includes the first port andthe second port or the hydraulic actuator includes the first port andthe second port, the first port is configured to allow fluid to flowfrom the pump to the hydraulic actuator, and the second port isconfigured to allow the fluid to flow from the hydraulic actuator to thereservoir tank.

In some embodiments, receiving identification information and connectioninformation for the first hose includes receiving identificationinformation and connection information via passive tag radio-frequencyidentification (RFID), active tag RFID, near-field communication (NFC),near-field magnetic induction (NFMI), Bluetooth, or Wi-Fi.

In some embodiments, receiving identification information and connectioninformation for the first hose includes receiving receive identificationinformation and connection information via a passive RFID tag coupled tothe first hose and an active RFID reader proximate to the first port,the active RFID reader configured to read the passive RFID tag todetermine the identification information for the first hose.

In some embodiments, determining a connection fault based on at leastone of the identification information and connection informationincludes determining that the first hose has disconnected from the firstport. In some embodiments, providing a notification of the connectionfault includes providing an indication of the first hose beingdisconnected from the first port to the monitoring device.

Another implementation of the present disclosure is a hose apparatus fora hydraulic system. The hose apparatus includes a first hose configuredto fluidly couple a pump with a hydraulic actuator using a first port.The first hose includes a first electronic device. The hose apparatusfurther includes the first electronic device configured to provideidentification information for the first hose to a transmitter, thetransmitter configured to provide a first connection signal using theidentification information for the first hose, the first connectionsignal used to determine a connection fault based on the firstconnection signal. Upon the first hose fluidly coupling the pump using adifferent port, the hydraulic system is automatically adjusted such thatthe first hose fluidly couples the pump with the hydraulic actuatorusing the different port.

In some embodiments, the hose apparatus further includes a second hoseconfigured to fluidly couple the hydraulic actuator with a reservoirtank using a second port. The second hose includes a second electronicdevice configured to provide a second connection signal using theidentification information for the second hose, the second connectionsignal used to determine the connection fault based on the secondconnection signal.

In some embodiments, the hose apparatus further includes a controller.The controller is configured to determine that the connection fault isbased on at least one of the first hose fluidly coupling the pump usingthe second port or the second hose fluidly coupling the reservoir tankusing the first port. The controller is further configured to adjustinternal operation of the hydraulic system to fluidly couple the pumpwith the hydraulic actuator using the first hose and to fluidly couplethe hydraulic actuator with the reservoir tank using the second hose.

In some embodiments, the hose apparatus further includes a hydraulicmanifold, the hydraulic manifold including the first port and the secondport or the hydraulic actuator including the first port and the secondport. In some embodiments, the first port is configured to allow fluidto flow from the pump to the hydraulic actuator and the second port isconfigured to allow the fluid to flow from the hydraulic actuator to thereservoir tank.

In some embodiments, the transmitter and the first electronic devicecommunicate via passive tag radio-frequency identification (RFID),active tag RFID, near-field communication (NFC), near-field magneticinduction (NFMI), Bluetooth, or Wi-Fi.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of a vehicle, according to someembodiments.

FIG. 2A is a block diagram of an open loop hydraulic system which can beimplemented in the vehicle of FIG. 1, according to some embodiments.

FIG. 2B is a block diagram of a closed loop hydraulic system that can beimplemented in the vehicle of FIG. 1, according to some embodiments.

FIG. 3 is a diagram of an electronic device for detecting hydraulic hoseconnections which can be implemented in the hydraulic systems of FIGS.4A-B, according to some embodiments.

FIG. 4A is a block diagram of a control system for detecting hydraulichose information which can be implemented in the hydraulic systems ofFIGS. 4A-B, according to some embodiments.

FIG. 4B is a block diagram of a controller for detecting hydraulic hoseinformation, which can be implemented in the control system of FIG. 4A,according to some embodiments.

FIG. 5 is a diagram of a hydraulic manifold which can be implemented inthe hydraulic systems of FIGS. 4A-B, according to some embodiments.

FIG. 6A is a diagram of a faulty hydraulic system that can beimplemented in the vehicle of FIG. 1, according to some embodiments.

FIG. 6B is a diagram of a corrected hydraulic system that can beimplemented in the vehicle of FIG. 1, according to some embodiments.

FIG. 7 is a flow diagram of a process for monitoring hydraulic hoseconnections which can be performed by the controller of FIG. 4A,according to some embodiments.

FIG. 8 is a flow diagram of a process for detecting hose operationhazards which can be performed by the controller of FIG. 4A, accordingto some embodiments.

FIG. 9 is a flow diagram of a process for detecting disconnected hoseswhich can be performed by the controller of FIG. 4A, according to someembodiments.

DETAILED DESCRIPTION Overview

Referring generally to the FIGURES, systems and methods for monitoringhose connections to a hydraulic manifold are shown, according to someembodiments. The monitoring may be performed using electronicidentifiers pertaining to each hose: one coupled to the outlet of theone hydraulic hose and one proximate to the port in which the hydraulichose is connecting to. The two electronic identifiers may communicatewith one another to determine which hose has connected to which port.For example, the system can determine if an outlet hose from a hydraulicpump is coupled to the pump port on the hydraulic manifold (correct) orto the reservoir tank port on the hydraulic manifold (incorrect).

A controller may be implemented in the system that can analyze the hoseconnection data to determine if there is one or more faults associatedwith the connections. In the “incorrect” example above, the controllermay be able to determine that the configuration is incorrect based onpreviously stored information relating to correct system operation. Oncea fault has been detected, this information can be provided to a userfor notification purposes. In some embodiments, other faults can bedetected, such as hose specification faults and hose disconnect faults.

Furthermore, the controller may include functionality to automaticallyadjust the system to correct for the fault. While all faults may not beautomatically adjustable via the controller, some may be corrected bythe controller sending control signals to the system components. Stayingwith the “incorrect” example above, the controller may provide controlsignals to the hydraulic manifold that adjusts the valve positioningwithin the hydraulic manifold such that the pump ports and tank portsare routing fluid to the opposite locations, thus fixing the assemblyfault without disconnecting and appropriately re-connecting the hoses.

While the systems and methods disclosed herein generally refer to anopen hydraulic system (e.g., system 400 described below), this is merelymeant for simplicity purposes. As described in detail below, the systemsand methods described herein can be implemented in any number ofhydraulic control systems, such as those with closed-loop circuits(e.g., system 450, etc.). Furthermore, while hose 502 is generally usedto discuss hose connections within the system, this is also meant forsimplicity purposes and the systems and methods described herein may beimplemented with other hoses (e.g., reservoir tank hoses, port AB hoses,etc.).

As described herein, electronic devices can refer passive tags and/oractive tags, RFID tag readers, or any combination thereof. Electronicdevices may include devices with a power source (e.g., a battery-powereddevice, etc.), or no power source (e.g., passive RFID tag, etc.).Electronic devices are not limited to these descriptions and can includeother types of communication devices. For example, electronic devicesmay include Bluetooth beacons for Bluetooth communication, Wi-Fireceivers/transceivers for Wi-Fi communication, and near-filedcommunication devices. Furthermore, electronic devices may communicatewiredly and not over a wireless communications network.

As described herein, the systems and methods are generally implementedwithin work vehicle 10. Work vehicle 10 may include any type of heavymachinery, heavy equipment, or machinery in general that uses hydrauliccomponents during operation. For example, work vehicle 10 could includebe or include a skid steer loader, an excavator, a backhoe loader, awheel loader, a bulldozer, a telehandler, a motor grader, machines withhydraulic brakes, machines with power steering systems, machines withtransmissions, garbage trucks, refuse vehicles, aircraft flight andvehicles, and/or lifts.

As described herein, a hydraulic return component can refer to anyhydraulic component in which fluid is routed back to from the motor. Insome embodiments, the system is configured as an open loop system thatroutes fluid from the motor (e.g., motor 408) back to a reservoir (e.g.,reservoir tank 402), as shown in FIG. 2A, wherein the reservoir tankacts as the hydraulic return component. In other embodiments, the systemcan act as a closed loop hydraulic system where fluid is routed from themotor back to the hydraulic pump (e.g., pump 404), as shown in FIG. 2B.The term “hydraulic return component” may refer to hydraulic pumps,hydraulic reservoir tanks, or both.

As described herein, an actuator assembly can refer to any type ofdevice capable of converting hydraulic fluid pressure into mechanicalmotion via linear force, torque, or a combination thereof. In someembodiments, an actuator assembly includes a hydraulic cylinder. Inother embodiments, an actuator assembly includes a hydraulic motor(e.g., one-way hydraulic motor, two-way hydraulic motor, etc.). Whilethe systems and methods described herein generally refer to a hydraulicmotor, this should not be considered limiting and any actuator assemblymay be used to receive hydraulic fluid from a pump and actuator an endcomponent using the received hydraulic fluid.

Overall Vehicle

Referring now to FIG. 1, a diagram of work vehicle 10 and associatedagricultural implement 12 in accordance with aspects of the presentsubject matter. Specifically, FIG. 1 illustrates a perspective view ofwork vehicle 10 towing implement 12 along a direction of travel (e.g.,as indicated by arrow 14), with the implement 12 being unfolded into awork position. In so embodiments, hydraulic implement 12 is controlledand/or operated by one or more hydraulic systems. As shown in theillustrated embodiment, work vehicle 10 is configured as an agriculturaltractor. However, in other embodiments, the work vehicle 10 may beconfigured as any other suitable vehicle, such as a skid steer loader,an excavator, a backhoe loader, a wheel loader, a bulldozer, atelehandler, a motor grader, and/or another type of construction machineor vehicle. Work vehicle 10 may be or include any type of vehicle ormachine that uses hydraulic systems to move or operate one or moreimplements.

Work vehicle 10 is shown to include a pair of front track assemblies 16,a pair or rear track assemblies 18 and frame or chassis 20 coupled toand supported by the track assemblies 16, 18. Operator's cab 22 may besupported by a portion of chassis 20 and may house various input devicesfor permitting an operator to control the operation of one or morecomponents of work vehicle 10 and/or one or more components of implement12. Additionally, as is generally understood, work vehicle 10 mayinclude an engine (not shown) and a transmission (not shown) mounted onchassis 20. The transmission may be operably coupled to the engine andmay provide variably adjusted gear ratios for transferring engine powerto track assemblies 16, 18 via a drive axle assembly (not shown) (or viaaxles if multiple drive axles are employed). Work vehicle 10 may alsoinclude operator input and output devices, such as an operator interface(e.g., operator interface 632 described below).

It should be appreciated that the configuration of work vehicle 10described above and shown in FIG. 1 is provided only to place thepresent subject matter in an exemplary field of use. Thus, it should beappreciated that the present subject matter may be readily adaptable toany manner of work vehicle configuration. For example, in an alternativeembodiment, a separate frame or chassis may be provided to which theengine, transmission, and drive axle assembly are coupled, aconfiguration common in smaller tractors. Still other configurations mayuse an articulated chassis to steer work vehicle 10, or rely ontires/wheels in lieu of the track assemblies 16, 18. Additionally,although work vehicle 10 is shown in FIG. 1 as including cab 22 for anoperator, the work vehicle 10 may, instead, correspond to an autonomousvehicle, such as an autonomous tractor.

According to an exemplary embodiment, work vehicle 10 is an off-roadmachine or vehicle. In some embodiments, the off-road machine or vehicleis an agricultural machine or vehicle such as a tractor, a telehandler,a front loader, a combine harvester, a grape harvester, a forageharvester, a sprayer vehicle, a speedrower, and/or another type ofagricultural machine or vehicle. In some embodiments, the off-roadmachine or vehicle is a construction machine or vehicle such as a skidsteer loader, an excavator, a backhoe loader, a wheel loader, abulldozer, a telehandler, a motor grader, and/or another type ofconstruction machine or vehicle. In some embodiments, the work vehicle10 includes one or more attached implements and/or trailed implementssuch as a front mounted mower, a rear mounted mower, a trailed mower, atedder, a rake, a baler, a plough, a cultivator, a rotavator, a tiller,and/or another type of attached implement or trailed implement.

Vehicle Hydraulic System

Referring now to FIG. 2A, a block diagram of hydraulic system 400 whichcan be implemented in the vehicle of FIG. 1, according to someembodiments. System 400 may be configured as an open loop hydraulicsystem, wherein the fluid flow is continuous and the system pressure maybe intermittent. System 400 is shown to include reservoir tank 402,hydraulic pump (“pump”) 404, hydraulic manifold (“manifold”) 406,hydraulic motor (“motor”) 408 and tractive element 410. System 400 mayact as a hydraulic system for work vehicle 10 to move one or more endcomponents of work vehicle 10. For example, system 400 is configured toprovide hydraulic fluid to motor 408, creating torque on a driveshaftcoupled to tractive element 410, thus rotating tractive element 410. Inanother example, system 400 is configured to provide hydraulic fluid toa hydraulic cylinder for an excavator arm of work vehicle 10, displacingthe position of the cylinder and moving the excavator arm coupled to thecylinder.

System 400 may be configured as an open-loop hydraulic circuit. In someembodiments, system 400 provides a continuous flow of hydraulic fluid tomotor 408. Upon leaving motor 408, the fluid is returned to reservoirtank 402, which may be done without pumping the return hydraulic fluidto a high pressure. The configuration of system 400 as an open-loopcircuit may differ from other types of hydraulic systems (e.g.,closed-loop hydraulic circuits, etc.), which is described in greaterdetail below with reference to FIG. 2B.

System 400 is not limited the components described above and may includeother components typically found in hydraulic systems, such as controlvalves (e.g., pressure relief valves, pressure regulators, shuttlevalves, check valves, globe valves, etc.), accumulators, filters, tubes,pipes, hydraulic seals (e.g., elastomeric seals, face seals, beam seals,swaged seals, etc.), fittings (e.g., pipe fittings, flare fittings,etc.). Particularly, system 400 may include any number of hydraulichoses for transporting fluid throughout system 400. Types of hydraulichoses and their functionality that may be implemented in system 400 aredescribed below with reference to FIG. 3.

System 400 may generally refer to hydraulic systems and methods withinwork vehicle 10. While work vehicle 10 is described above to be anoff-road machine or vehicle, work vehicle 10 may also be any type ofequipment that implements hydraulic systems in their functionality, suchas tractors, excavators, backhoes, hydraulic brakes, power steeringsystems, transmissions, garbage trucks, refuse vehicles, aircraft flightvehicles, lifts, and industrial machinery.

Reservoir tank 402 may be configured to hold excess hydraulic fluid toaccommodate volume changes within system 400. These volume changes mayinclude but are not limited to cylinder extension, cylinder contraction,temperature driven expansion, temperature driven expansion, and/orleaks. As described herein, “fluid” or hydraulic fluid may refer to anytype of fluid capable of being pressurized and supplied to an actuationdevice (e.g., motor, ram, etc.) to actuate another component. In someembodiments, hydraulic fluid refers to any medium by which power istransferred in system 400. Reservoir tank 402 may be configured to aidin separation of air from the hydraulic fluid, work as a heataccumulator to cover losses in system 400 when peak power is used, andseparate dirt and other particulate from the oil. Reservoir tank 402 isshown to receive fluid from pressure relief lines and fluid lines frommanifold 406 and provide low-pressure fluid to pump 404.

While reservoir tank 402 is shown as a separate tank for which hydraulicfluid can be stored, reservoir tank 402 may also be a storage componentdirectly within pump 404. For example, instead of the fluid routing backfrom motor 408 to reservoir tank 402, the fluid is routed directly backto pump 404, and any additional fluid within pump 404 is consideredfluid storage within reservoir tank. In such embodiments, the flow ratemay be considered intermittent as there is less hydraulic fluid toextract from tank 402, but system pressure may remain generallyconstant.

For example, once fluid exits motor 408 after providing mechanicaltorque to the driveshaft of motor 408, the return fluid is routedthrough manifold 406 back to reservoir tank 402. If the pressure withinmotor 408 was too high, a pressure relief line from motor 408 may routeexcess fluid back to reservoir tank 402—reducing the internalpressure—to avoid damage to system 400. In some embodiments, pump 404may also experience unsafe pressure levels and result in the pumppressure relief line routing hydraulic fluid back to reservoir tank 402to avoid damage to system 400.

Pump 404 may be configured to supply fluid to the components in system400. In some embodiments, pump 404 may be configured to provide pressurein the system in reaction to the system load. For example, if pump 404is rated for 5,000 pounds per square inch (psi), pump 404 is capable ofmaintaining flow against a load of 5,000 psi. Pump 404 may be configuredas an axial piston pump in system 400 to vary output flow for automaticcontrol of pressure. This may allow system 400 maintain a constantpressure by varying the flow rate of the hydraulic fluid throughoutsystem 400. Other pumps may also be considered, such as gear pumps, vanepumps, and radial piston pumps. Pump 404 is shown to receive lowpressure fluid and provide high pressure fluid to manifold 406. Pump 404is also shown to include a pressure relief line back to reservoir tank402. In some embodiments, the pressure relief line from pump 404 is usedto reduce pressure by routing fluid back to reservoir tank 402 if thesystem pressure reaches a predetermined threshold.

Manifold 406 may be configured to regulate fluid flow within system 400.In some embodiments, manifold 406 may act analogously to an electricalswitchboard, as the operator can control how much fluid flows betweenwhich components of system 400. While system 400 only shows a singlehydraulic line entering manifold 406, multiple input and output linescan be considered, as can be typical in implementations of hydraulicmanifolds. Manifold 406 may include one or more assorted valves, theconfiguration of which being responsible for routing fluid through themanifold 406. In some embodiments, manifold 406 includes a controlmechanism (e.g., lever, button, slide, etc.) that allows for adjustmentto the routing of fluid within manifold 406. Manifold 406 may includeone or more hydraulic ports, described in greater detail below withreference to FIG. 3. Manifold 406 is shown to allow fluid from pump 404to provide port A fluid to motor 408. Manifold 406 is also shown toreceive port B fluid from 408, and facilitate transportation of the portB fluid back to pump 404 (e.g., via reservoir tank 402, etc.). In someembodiments, manifold 406 includes one or more solenoid valves to routefluid.

Manifold 406 may include one or more control valves that allows manifold406 to operate in one or more positions. In some embodiments, thisassembly of valves within a single housing may be referred to as thecenter control valve for the hydraulic system (e.g., system 400, system450, etc.). As an example, manifold 406 as shown in FIG. 2A containsthree separate positions, indicated by the three separate boxes withinthe component. As shown in FIG. 2A, manifold 406 is currently in the“open center” position, which connects all four ports together, allowingthe motor receive fluid in both directions (e.g., via port A and portB). Manifold 406 also includes a lever that can adjust whichconfiguration is currently engaged. For example, if a user pulls thelever, manifold 406 may transition from “open center” position to the“reversed” position (e.g., the far right position). Manifold 608 and thevarious valve configurations therein are not limited to being controlledby a lever and can also be controlled manually, via a solenoid, a pushbutton, a pedal, compressed air, a fluid pilot, or a cam.

In some embodiments, manifold 406 can change the valve position based ona signal sent from a controller. This may be advantageous if a controlsystem monitoring system 400 determines that there is an error (e.g.,error signal, incorrect installation, etc.) that can be solved byplacing the center control valve (e.g., manifold 406) in a differentposition. This is described in greater detail below with reference toFIG. 8.

Motor 408 may be configured to convert the hydraulic pressure providedby pump 404 to torque, force, rotational displacement, lineardisplacement, or any combination thereof. While motor 408 is describedas a “motor” (e.g., a rotary device), a hydraulic cylinder in place ofmotor 408 may also be considered. This is shown by hydraulic cylinder409. Similar to motor 408, hydraulic cylinder 409 may be configured as adouble-acting cylinder to operate in bother directions. In one example,motor 408 is configured to receive hydraulic fluid from pump 404 androtate a driveshaft coupled to tractive element 410. In another example,hydraulic cylinder 409 receives hydraulic fluid from pump 404 via port Aand displaces the cylinder to move an excavator arm work vehicle 10.

In some embodiments, motor 408 is configured to convert the fluidpressure to mechanical force/torque in both directions (e.g., a two-waymotor, etc.). For example, manifold 406 may be controlled to adjust fromthe configuration shown in FIG. 2A to a configuration that switches theport A fluid line and port B fluid line. This may be done by slidingmanifold 406 into the far right configuration (e.g., via the lever,etc.). Subsequently, high-pressure fluid from pump 404 would be providedto the other side of motor 408 (e.g., port B) while the fluid would exitmotor 408 from the top line (e.g., port A).

Referring now to FIG. 2B, a block diagram of a closed loop hydraulicsystem 450 is shown, according to some embodiments. In some embodiments,system 450 may incorporate some or all of the features, descriptions,and components shown in FIG. 2A. For example, system 450 may alsoinclude manifold 406. In another example, system 450 may include controlvalves (e.g., pressure relief valves, pressure regulators, shuttlevalves, check valves, globe valves, etc.), accumulators, filters, tubes,pipes, hydraulic seals (e.g., elastomeric seals, face seals, beam seals,swaged seals, etc.), fittings (e.g., pipe fittings, flare fittings,etc.).

In some embodiments, system 450 is configured as a closed-loop hydrauliccircuit, where pump 404 supplies a continuous (e.g., or near continuous)flow with varying pressure. Pump 404 may vary the provided flow rate,pumping little to no hydraulic fluid to the one or more control valvesuntil a signal (or user operation) actuates one of the control valves,thereby reducing an open-center return path (e.g., via manifold 406 asshown in FIG. 2A) back to reservoir tank 402. System 450 is shown toinclude reservoir tank 402, pump 404, charge pump 452, check valves 456,458, charge relief valve 454, motor 408, and tractive element 410.System 450 may act as another embodiment for which the systems andmethods for monitoring hose connections may be implemented.

In a general embodiment, pump 404 provides continuous flow to motor 408.To avoid overly high temperature of the fluid, charge pump 452 may beconfigured to pump lower-temperature fluid into the high pressure (top)line of system 450, thereby reducing the temperature of the fluid.Charge pump 452 may also be configured to receive the lower-temperaturefluid from tank 402. Several check valves 456, 458 may be used thatallow the fluid to flow from the inner loop to the outer loop (and viceversa). Charge relief valve 454 may be configured to provide pressurerelief in the system via a spring/pilot configuration. If the pilot linereaches a high enough pressure to compress the spring, fluid can berouted to tank 402 for relief.

Hydraulic System Hose Identifiers

Referring now to FIG. 3, a diagram 500 for detecting hydraulic hoseconnections via electronic devices is shown, according to someembodiments. Diagram 500 is shown to include hydraulic hose (“hose”)502, passive tag 504, hydraulic manifold 406, hydraulic connectors 506,510, and tag readers 508, 512. In some embodiments, diagram 500 showstag reader 508 reading passive tag 504 upon connection of hose 502 withhydraulic connector 506. Tag reader may then process and/or provide thereceived data to one or more processing devices (e.g., systemcontrollers, mobile devices, workstations, etc.). These and otherembodiments are described in greater detail below.

Hydraulic hose 502 may be any type of hydraulic hose, hydraulic pipe, orhydraulic tube configured to couple one or more hydraulic systemcomponents (e.g., pump 404, motor 408, etc.) with other hydrauliccomponents, such as the hydraulic ports on hydraulic manifold 406.Systems 400, 450 may include any number of hoses similar to hose 502 forrouting hydraulic fluid throughout the systems. In some embodiments,hose 502 includes both rubber and steel layers to provide enoughdurability to withstand the system pressures, but enough flexibility forsimple installation and maintenance. In some embodiments, a rubberinterior of hose 502 is surrounded by multiple layers of woven wire andrubber.

Hydraulic hose 502 may include passive tag 504 proximate to the end ofhose 502 that will couple to hydraulic connector 506. In someembodiments, passive tag 504 is located on the outside of hose 502. Forexample, passive tag 504 is a passive radio-frequency identification(RFID) tag that is taped, glued, soldered, magnetically coupled, ormounted to the outside of hose 502. In some embodiments, passive tag 504is located on the inside of hose 502. For example, passive tag 504 maybe a fluid-proof (e.g., not damaged by hydraulic fluid) passive RFID tagmounted inside of hydraulic hose 502. In such embodiments, tag readers508, 512 may be strong enough to transmit signals that pass through thelining of hose 502 to reach passive tag 504 and receive the returnsignals from passive tag 504. In some embodiments, passive tag 504includes data on which component is being coupled to connector 506. Forexample, a metal terminal near pump 404 electrically connects with ametal terminal on hose 502 (not shown). The metal terminal is connectedto passive tag 504 that indicates what hose 504 has connected to. Thisinformation may be relayed to tag reader 508 upon RFID transmission.

Tag reader 508 may be configured to transmit a read signal that, whenhose 502 is coupled to hydraulic connector 506, can be received bypassive tag 504. For example, tag reader 508 is wired directly to apower source and continuously transmits an RFID read signal. Hose 502 iscoupled to hydraulic connector 506. Passive tag 504 receives the RFIDread signal and provides a response signal back to tag reader 508. Tagreader 508 then provides the response signal to a processing device. Inanother example. tag reader 508 is battery operated and provides andRFID read signal when instructed. Hose 502 is coupled to hydraulicconnector 506. An operator of a control system monitoring system 400provides instructions to run a diagnostics report of the connected hosesto manifold 406. Tag reader 508 subsequently sends the RFID read signal,which is received by passive tag 504. Passive tag 504 provides aresponse signal to tag reader 508 in response and tag reader 508 sendsthe response signal to a processing device. The processing devicedetermines whether there is an issue with the connection and relays thatinformation to the user. Other examples are described in greater detailbelow (see FIG. 8). While tag readers 508, 510 are shown to be discretecomponents, a single tag reader may be used to monitor all hoseconnections on manifold 406.

Hydraulic connector 506 may fluidly connect to the outlet of hose 502.This may be performed using one or more coupling features, such as anotched lock, mechanical latches, magnetic latches, or fasteners.Hydraulic connector is shown to connect hose 502 to port P, as describedabove with reference to FIG. 2A) indicating that hose 502 is couplingfrom pump 404 to manifold 406 via hydraulic connector 506 at port P. Asmentioned, the systems and methods described herein for monitoring andcorrecting hose connections can apply to any hose and/or any portconfiguration described herein. For example, another passive tag islocated on the hose coupling reservoir tank 402 to hydraulic connector510 (not shown).

In some embodiments, the connection between hose 502 and hydraulicconnector 506 is not monitored via passive tag 504 and tag reader 508.In other embodiments, the connection may be monitored mechanically. Forexample, each of the hoses connecting to hydraulic manifold 406 may usea particular coupling mechanism that can only connect to its correctport. In this example, hose 502 would only be able to couple tohydraulic connector 506. This would prevent hose 502 from coupling tothe wrong port (e.g., port 510, etc.). However, this may require a lackof universality between most hydraulic hoses in the industry, which isatypical.

While RFID communication is used as the means for detecting hoseconnection information (e.g., the methods performed in system 500,etc.), this is merely meant to be exemplary and should not in any way beconsidered limiting. Any electrical circuitry that is capable ofproviding information related to the connection of hose 502 to connector506 should be considered. For example, hose 502 could include a metalterminal that electrically connects to another metal terminal uponcoupling with connector 506. In another example, a user may directlyconnect (e.g., via an wire harness, etc.) circuitry from hose 502 tocircuitry on manifold 406 after coupling hose 502 to connector 506. Inanother example, hose 502 includes near-filed communication (NFC)technology that provides hose identification information and/or hoseconnection information to another NFC component on manifold 406. Othermeans of communicating data between hose 502 and tag reader 506 may beused, such as Bluetooth, Wi-Fi, Zigbee, Zwave, XBee, near-field magneticinduction (FMI), or any other communication means typically used underNFC, body area networks (BAN), personal area networks (PAN), near-mearea networks (NAN), and local area networks (LAN).

Hydraulic Control System

Referring now to FIG. 6, a control system 600 for monitoring theassembly and/or operation of hydraulic system 400 and/or system 450 isshown, according to some embodiments. Control system 600 may beimplemented entirely within work vehicle 10 (e.g., via one or moreprinted circuit boards within an electrical housing, within the cab,etc.) or partially within work vehicle 10 (e.g., the controller islocated in an off-premise server and is accessed via a mobile device orlaptop, etc.). Control system 600 may be configured to receive data fromelectrical identifiers (e.g., passive tag 504, tag reader 508, etc.) andprovide control signals, fault notifications, and other signals inresponse to processing the received data. Control system 600 is shown toinclude controller 602, hydraulic manifold 406, user device 630, andoperator interface 508.

Hydraulic manifold 406 is shown to include several circuits, (includingport P circuit 120) up to “n” number of circuits, indicated by port ncircuit 628. These circuits may include the functionality of tag readers508, 510 as described above with reference to FIG. 3. Port P circuit 620is shown to include tag reader manager 622, analyzer 624, andtransmission circuit 626. In some embodiments, all of the functionalityperformed by port P circuit via these components may be performed bymore or less components.

Tag reader manager 622 may be configured to receive port P tag data andprovide ID/specification information to analyzer 624. In someembodiments, port P circuit 620 is responsible for receiving data frompassive tag 504. Hydraulic manifold 406 may include any number ofcircuits for monitoring the multiple connections (e.g., one circuit perport connection, etc.). In some embodiments, the port P tag dataincludes a particular hose ID signal that indicates the type of hosethat hose 502 is. This hose ID signal may also include specificationdata about the hose, such as maximum pressure threshold, diameter,length, etc. In some embodiments, the port P tag data also includesconnection information that indicates to tag reader manager 622 whatport hose 502 is supposed to connect to. For example, upon receiving areturn RFID signal from passive tag 504, tag reader manager 622 receivesdata that indicates hose 502 is the hose that has been coupled toconnector 506, that hose 502 is a reinforced rubber hydraulic hose at ⅜in.×48 in.L, rated for 4,000 PSI, and made by Apache, Co. Tag readermanager 622 can provide this information to analyzer 624.

Analyzer 624 may receive the ID/specification information and separatethe data into connection data and fault signals. In some embodiments,the fault signals may be provided if there is a clear error with thesignal. For example, hose 502 has been connected but no signal has beenreceived by passive tag 504. Other faults—such as faults determined byanalyzing the port P tag data—may be determined by controller 602 aftertransmission. Analyzer 624 may provide the connection data and/or faultdata to transmission circuit 626 for transmitting to controller 602.

Controller 202 is shown to include communications interface 618 andprocessing circuit 604 including processor 606 and memory 608.Processing circuit 604 can be communicably connected to communicationsinterface 618 such that processing circuit 604 and the variouscomponents thereof can send and receive data via communicationsinterface 618. Processor 606 can be implemented as a general purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable electronic processing components.

Communications interface 618 can be or include wired or wirelesscommunications interfaces (e.g., jacks, antennas, transmitters,receivers, transceivers, wire terminals, etc.) for conducting datacommunications with building subsystems 428 or other external systems ordevices. In various embodiments, communications via communicationsinterface 618 can be direct (e.g., local wired or wirelesscommunications) or via a communications network (e.g., a WAN, theInternet, a cellular network, etc.). For example, communicationsinterface can include an Ethernet card and port for sending andreceiving data via an Ethernet-based communications link or network. Inanother example, communications interface 618 can include a Wi-Fitransceiver for communicating via a wireless communications network. Inanother example, communications interface 618 can include cellular ormobile phone communications transceivers.

Memory 608 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent disclosure. Memory 608 can be or include volatile memory ornon-volatile memory. Memory 208 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present disclosure. According to an exampleembodiment, memory 608 is communicably connected to processor 606 viaprocessing circuit 604 and includes computer code for executing (e.g.,by processing circuit 604 and/or processor 606) one or more processesdescribed herein.

In some embodiments, controller 602 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments controller 602 can be distributed across multiple servers orcomputers (e.g., that can exist in distributed locations). Memory 208 isshown to include data collector 610, fault manager 612, alert manager614, and hydraulic manifold adjustment manager 616.

Data collector 610 may be configured to receive the connection dataand/or fault data from the circuit(s) coupled to hydraulic manifold 406and provide the data to fault manager 612. Fault manager 612 may beconfigured to analyze the data to determine if one or more actions(e.g., notifications, corrective actions, etc.) needs to be taken. Forexample, fault manager 612 processes the received data and determinesthat hose 502 was coupled to hydraulic manifold 406 via hydraulicconnector 510. In this example, this is problematic, as hose 502 istherefore connecting pump 504 to the outlet of a one-way motor via portT (connector 510). Fault manager 612 determines this and provides asignal to alert manager 614 to notify a user. Other examples areconsidered and described in greater detail below.

Alert manager 612 may be configured to manage the multiple alerts thatmay be generated based on the received hose connection data. In oneexample, alert manager 614 may provide a notification to user device 630via operator interface 508 that alerts the user that there is a fault.For example, following an incorrect hose connection on work vehicle 10,a user checks the vehicle tablet (e.g., user device 630) and sees anotification that states: “STOP: PUMP HOSE MISCONNECTED.” In someembodiments, the fault can be fixed manually by the user orautomatically by controller 602. If the controller 602 corrects thefault automatically, hydraulic manifold adjustment manger 616 mayprovide control signals to hydraulic manifold 406 to adjust internaloperation of the manifold such that the port configuration places thesystem in the correct orientation without disconnecting the hoses andreconnecting them the correct way.

Referring now to FIG. 4B, a block diagram of controller 602 is shown,according to some embodiments. Controller 602 is shown to includeprocessing circuit 604 including processor 606 and memory 608. Memory608 is shown to include data collector 610, fault manager 612, alertmanager 614, and hydraulic manifold adjustment manager 616. In someembodiments, FIG. 4B provides a more detailed illustration of controller602 as described above with reference to FIG. 4A.

Data collector 610 may receive hose connection data and provide the datato fault manager 612. In some embodiments, data collector 610 candetermine the hose/port configurations that have been provided. Forexample, data collector 610 can determine that hose 502 has beenconnected to connector 510 (fluidly coupling port T) and provide thatinformation to fault manager 612 for analytics.

Fault manager 612 may be configured to analyze the hose connection dataand determine whether a signal needs to be provided to alert manager 614in the event of a fault. In some embodiments, fault manager 612determines that there is no fault in system 600 and still provides anotification to a user (e.g., via operator interface 508, etc.)indicating that the assembly of the hydraulic system 400 or 450 has beenassembled correctly. Fault manager 612 may receive data on the correcthose configurations, such as which types of hoses are supposed to beconnected to which ports, which hoses should not be connected to whichports, etc. This data may be stored locally (e.g., in database 620,etc.) on controller 602 or received from an external device (e.g., via aserver on a cloud, etc.). Fault manager 612 may compare the correct hoseconfigurations with the hose configurations received via the hoseconnection data and determine if a fault has occurred.

For example, fault manager 612 receives data that indicates hose 502 hascoupled pump 404 to connector 510. Fault manager compares this to thedata on correct hose confirmations, which indicates that pump 502 issupposed to be connected to connector 508 (port P), to rout fluid tomotor 408. Instead, hose 502 has been connected to port T, which issupposed to route fluid to reservoir tank 402. As such, routing thefluid from pump 404 through port P to reservoir tank 402 via port T, isthe incorrect configuration. Fault manager 612 subsequently provide a“detected assembly fault” signal to alert manager 614. Alert manager 612may receive this fault signal and determine that this fault can be fixedautomatically. Alert manager 612 proceeds by sending a faultnotification to operator interface 632 and by sending a correctionsignal to hydraulic manifold adjustment manager 616 to perform acorrective action. Hydraulic manifold adjustment manager 616 determinesthat the fault may be corrected by providing a control signal tohydraulic manifold 406 that switches the “position” of the valveconfiguration from “open center” position to “reversed” position.Hydraulic manifold adjustment manager 616 provides a control signal toan actuator configured to control the valve positions for hydraulicmanifold 406 to switch the port configurations and correct the fault. Insome embodiments (not shown), controller 602 may receive a signal thatthe automatic corrective action has been completed. Upon receiving thissignal, alert manager 614 may provide another signal to operatorinterface 632, indicating that the automatic fault correction has beencompleted.

In some embodiments, fault manager 612 may receive standard operationaldata from operational database 620. This data may indicate thespecifications of the identified hose, such as pressure ratings, correctconfigurations, length (2 m., 5 m., etc.), diameter, types of fluidsthat it can receive (e.g., brake fluid, power steering fluid, mineraloil-based fluid, water-based fluid, etc.), and intended use (e.g.,tractor system, excavator system, etc.). Fault manager 612 may alsocompare the standard operational data with the received hose data. Forexample, fault manager 612 receives hose data relating to hose 502connecting to connector 508. Fault manager 612 determines that this isthe correct hose for coupling pump 504, but determines that the hose isout of specification due to the hose not being strong enough to handlethe pressure within system 400. Fault manager 612 then provides adetected assembly fault to alert manager 614. Alert manager 614determines that this fault cannot be fixed automatically and proceedswith sending (i) a notification signal to operator interface 632 toalert the user of the detected fault and (ii) a message to operatorinterface 632 detailing the fault and steps on how to correct it. Inthis example, the message may include details on the proper hose(s) thatshould be connected to port 508.

In some embodiments, fault manager 612 determines that a hose has beendisconnected in real-time. For example, tag reader 508 may continuouslybe transmitting hose data to controller 602 to verify that hose 502 isstill coupled to port 508. During operation of work vehicle 10, hose 502disconnects from port 508. Port P circuit 620 provides this informationto controller 602. Fault manager 612 then determines an unconnected hosefault and provides alert manager 614 with a signal to alert the user ofwork vehicle 10 (e.g., via operator interface 632). As this fault maynot be corrected automatically, hydraulic manifold adjustment manager616 does not provide any control signals for corrective action. In someembodiments, manager 616 may provide signals to pump 404 and/or motor408 to stop operation of system 400 for safety purposes (e.g., followingdetection of a fault, etc.).

In some embodiments, data relating to the hose connections can beprovided by the user of work vehicle 10 via operator interface 632. Forexample, an application on operator interface 632 an be used to senddata to controller 602. A user may provide hose specifications regardingthe hoses that were connected. Fault manager 612 can then receive thisdata and compare it to the standard operational data to determine if theattached hoses will be in compliance and/or safe for operation. Otherdata may also be supplied by a user of operator interface 632 via theapplication, such as hose/port configurations, operating limitations(e.g., maximum system pressure, maximum pump speed, maximum flow rate,etc.), and customization of the corrective actions (e.g., alwaysadjusting the manifold, deciding to switch motor operation rather thanadjusting manifold position, etc.).

Referring now to FIG. 5, a detailed diagram of hydraulic manifold 406.Manifold 406 is shown to include ports 702, 704, hoses 706, frame 708,and implement 710. Manifold 406 may include any number of implements,and each implement may have several identifiers corresponding to each ofthe ports located on the implement. For example, implement 710 is shownto have 6 valves. Each valve may correspond to a unique identifier(e.g., valve 1 corresponds to ID 1, valve 2 corresponds to ID 2, etc.).Each implement configuration may be saved to memory of controller 602,such that all of the unique ID's of each of the hoses are also saved.This may allow the user to plug hoses into any port of implement 710 andcontroller 602 can configure manifold 406 to provide properfunctionality.

In some embodiments, a user can enter preferred operating credentialsfor manifold 406. For example, a user enters how the correctconfiguration on how the system should be assembled. Once the system isassembled, electronic identifiers communicate the assembly to controller602, where the assembly is different than the correct configuration.Controller 602 can then adjust the internal operation of manifold 406 tomatch the preferences entered by the user. This can allow the system tobe connected in any fashion, and the valve configuration can be adjustedto match the preferences provided.

In some embodiments, a user can enter preferred operating credentialsfor each particular hose. Memory 608 may then store the preferences foreach hose, where the electronic identifiers for each hose provide aunique identification that corresponds to the operating conditions foreach hose. When the hose data is received, controller 602 can adjust theoperation of system 400 (e.g., adjust internal operation of manifold406) to match the preferred preferences of one or more of the hoses.

In some embodiments, the manifold 406 can have a bank of general ports,some or all of which may not be specifically dedicated to particularimplements. For example, hose 502 is not necessarily dedicated toattached to port P. Controller 602 may receive the signals identifyingthe connects and control valves in the manifold to route hydraulic fluidand perform the indicated control operations based on the connections,such that the user can connect the multiple hoses to any port that isconvenient. This may require adjusting the interior operation of valve406 (e.g., moving the valve positioning as shown in FIGS. 6A-B).

Referring now to FIGS. 8A-B, diagrams for showing fault correction ofhydraulic system 400 are shown, according to some embodiments. FIG. 6Ashows system 400 with an incorrect hose configuration, while FIG. 6Bshows the system 400 after correction. In FIG. 6A, pump 404 has beenconnected to port T, which—as manifold 406 is currently configured, issupposed to route fluid from the outlet of motor 408 to reservoir tank402. Additionally, port P has been connected back to reservoir tank 402.As such, the fluid cannot flow from pump 404, through motor 408, andback to reservoir tank 402.

Controller 602 may detect this issue using similar methods describedabove with reference to FIGS. 6A-B. Once detected, controller 602 maycorrect the fault by changing the port configuration of hydraulicmanifold 406. This is shown in FIG. 6B, wherein hydraulic manifold isnot in the “reverse” position, which fluidly connects port T with portA, and port P with port B, thus allowing fluid to flow throughout thesystem. This single example is merely meant to be exemplary and shouldnot be considered limiting in any way. Several other portconfigurations, positions, and adjustments to the system may beimplemented to correct for assembly faults.

Control System Process

Referring now to FIG. 7, a process 900 for monitoring and adjusting forfault connections in a hydraulic system of a vehicle is shown, accordingto exemplary embodiments. Process 900 may be performed by any one of theprocessing components described herein, such as controller 602. Process900 may be performed automatically, based on instruction from a user, orbased on received data.

Process 900 is shown to include receiving connection data from a tagreader for a hydraulic hose coupled to a hydraulic manifold (step 902).In some embodiments, connection data can be received from the electronicidentifiers (e.g., passive tag 504, tag reader 508, etc.) that are usedto transmit and receive data regarding hose 502 and the characteristicsthereof. Connection data may also include determining what port hose 502has connected to. This may be done my using an identifier relating hose502 (e.g., ID-4, etc.) that, when a signal with the identifier isreceived, the signal can be analyzed to determine that the identifierrepresents hose 502. For example, when tag reader 508 transmits an RFIDsignal to passive tag 504, the identifier is provided back to tag reader508 and determines that hose 502 is the hose coupled to connector 506.

Process 900 is shown to include receiving correct hose configurationdata from a database (step 904). In some embodiments, fault manager 612receives other sets of data that indicate proper assembly and/oroperation of hydraulic system 400. For fault manager 612 to determine ifhose 502 has been coupled to the correct port, fault manager 612 mayhave a priori data on all correct hose/port configurations. This may bestored locally within memory 608, or received (e.g., wired orwirelessly) via an external source (e.g., cloud, Wi-Fi, etc.).

Process 900 is shown to include comparing the received connection datato the correct hose configuration data to determine if there is anassembly fault (step 906). Comparing the received connection data to thecorrect hose configuration may simply include determining whether the IDtag of the received connection data matches the correct ID tag stored inthe database. If an assembly fault is detected (step 908), alert manager614 may then determine whether the fault can be automatically adjusted(step 910). If a fault has been detect and the assembly can beautomatically adjusted to correct for the fault, alert manager 614 maythen provide instructions for hydraulic manifold adjustment manager toadjust the valve positions in such a way that system 400 may operatecorrectly without reassembling the hoses (step 912). If a fault isdetected and it cannot be automatically adjusted, a notification may beprovided to operator interface 632 (step 914) indicating that the faultneeds to be corrected (an example of this is shown in FIG. 9). If nofault has been detected, a notification may be sent to operatorinterface 632 (step 914) indicating that assembly/operation is correct.

Referring now to FIG. 8, a process 1000 for monitoring and adjusting forsafety hazards in a hydraulic system of a vehicle is shown, according toexemplary embodiments. Process 1000 may be performed by any one of theprocessing components described herein, such as controller 602. Process1000 may be performed automatically, based on instruction from a user,or based on received data.

Process 1000 is shown to include receiving hose specification data froma tag reader for a hydraulic hose coupled to a hydraulic manifold (step1002). In some embodiments, tag reader 508 provides specification datarelating to hose 502 to controller 602. As discussed above, this datacan relate to the actual operative properties of the hose. In someembodiments, the data can also include operative properties relating tothe component in which the hose is connecting to from the other hose end(e.g., pump 404).

In some embodiments, these operative properties of the hose includediameter, length, pressure ratings, and/or intended applications. Thisdata may be provided to controller 602 such that controller 602 candetermine if these operative properties will be sufficient forimplantation of hose 502 in system 400. For example, if the maximumpressure rating for hose 502 was below the intended pressure levels ofthe system, and controller 602 was aware of the intended pressure levelsof the system, controller 602 may be able to determine that hose 502 maycause a safety issue if implemented within system 400.

Process 1000 is shown to include receiving correct hose operation datafrom a database (step 1004). Controller 602 may receive the correct hoseoperation data from a database stored within memory 608, or from anexternal device. For example, an operator or user using operatorinterface 632 may input the information directly into controller 602 viaoperator interface 632.

Process 1000 is shown to include the comparing the hose specificationdata to the correct hose operation data to determine if there is apotential safety hazard (step 1006). Comparing the received hosespecification data to the correct hose operation data may includecomparing to find an exact match in the data or comparing to find if thereceived hose specification data is within a certain threshold thatwould be considered acceptable for operation. For example, if—based onthe stored operation data—if the system typically operates within apressure range of 2400-4000 psi, and hose 502 is rated for 2500-3900psi, this may be considered an acceptable hose implantation. In anotherexample, controller 602 may indicate a safety hazard for any hose thatdoes not exactly match the intended hose diameter of ⅜ in.

Process 1000 is shown to include a determination step to determinewhether there is a potential safety hazard that has occurred from theconnection of hose 502 (step 1008). Fault manager 612 may determine thatthere is a fault using the analytics described above and proceed to senda fault signal to alert manager 614. Process 1000 is shown to includeanother determination step to determine whether the fault can beautomatically fixed (step 1010). In some embodiments, these operationfaults may be automatically adjusted by lowering the flow rate of thepump or adjusting the motor speed to change the system operation so thathose 502 is now within specification (step 1012). In other embodiments,the operation fault is not fixed automatically and a notification isprovided to operator interface 632 to notify a user of the fault (step1014).

Referring now to FIG. 9, a process 1100 for monitoring hose connectionsand detecting a disconnected hose during operation, according toexemplary embodiments. Process 1100 may be performed by any one of theprocessing components described herein, such as controller 602. Process1100 may be performed automatically, based on instruction from a user,or based on received data.

Process 1102 is shown to include monitoring hose connections tohydraulic manifold (step 1102). In some embodiments, tag reader 508 orother means for monitoring the hose connections (as described above) maycontinually monitor the connection before, during, or after operation ofwork vehicle 10 (e.g., as mentioned in step 1104). For example, tagreader 508 continuously sends a signal to passive tag 504 to make surethat hose 502 is still connected to connector 506 when work vehicle 10is turned on or when hydraulic system 400 is implemented.

Process 1100 is shown to include receiving indication that one of thehoses connected to the hydraulic manifold has been disconnected (step1106). Process 1100 is also shown to include determining exact hose thathas been disconnected based on information provided by electronicidentifiers (step 1108).

In some embodiments, while work vehicle 10 is moving for example, one ofthe hoses connected to manifold 406 becomes disconnected. Tag reader 508may continuously monitor for a return signal from passive tag 504, andtherefore fails to receive one upon disconnection. Port P circuit 620may include processing that allows port p circuit 620 to transmit asignal to controller 602 indicating that no return signal was receivedby passive tag 504. Either port P circuit 620 or controller 602 maydetermine that this is indicative of a disconnected hose. In otherembodiments, this may be indicative of a failed passive tag.

Process 1110 is shown to include shutting off the hydraulic system ofthe vehicle (step 1110). Once the “hose disconnected” fault has beendetected, controller 602 may shut off work vehicle 10 or at leasthydraulic system 400 for safety purposes, as there may be a chance thata hose being disconnected can result in potential damage or danger tothe operator, system 400, work vehicle 10, or any combination thereof.In some embodiments, the operator may do this without the controlleronce he/she becomes aware of the fault. Process 1100 is shown to includeprovide notification to operator interface regarding the disconnectedhose (step 1112). In some embodiments, notifications regarding thedetection of the fault, how to fix the fault, an indication that thesystem(s) have been shut down for safety purposes, or other updates canbe relayed to the user via operator interface 632.

Configuration of Exemplary Embodiments

As utilized herein, the terms “approximately,” “about,” “substantially”,and similar terms are intended to have a broad meaning in harmony withthe common and accepted usage by those of ordinary skill in the art towhich the subject matter of this disclosure pertains. It should beunderstood by those of skill in the art who review this disclosure thatthese terms are intended to allow a description of certain featuresdescribed and claimed without restricting the scope of these features tothe precise numerical ranges provided. Accordingly, these terms shouldbe interpreted as indicating that insubstantial or inconsequentialmodifications or alterations of the subject matter described and claimedare considered to be within the scope of the disclosure as recited inthe appended claims.

It should be noted that the term “exemplary” and variations thereof, asused herein to describe various embodiments, are intended to indicatethat such embodiments are possible examples, representations, orillustrations of possible embodiments (and such terms are not intendedto connote that such embodiments are necessarily extraordinary orsuperlative examples).

The term “coupled” and variations thereof, as used herein, means thejoining of two members directly or indirectly to one another. Suchjoining may be stationary (e.g., permanent or fixed) or moveable (e.g.,removable or releasable). Such joining may be achieved with the twomembers coupled directly to each other, with the two members coupled toeach other using a separate intervening member and any additionalintermediate members coupled with one another, or with the two memberscoupled to each other using an intervening member that is integrallyformed as a single unitary body with one of the two members. If“coupled” or variations thereof are modified by an additional term(e.g., directly coupled), the generic definition of “coupled” providedabove is modified by the plain language meaning of the additional term(e.g., “directly coupled” means the joining of two members without anyseparate intervening member), resulting in a narrower definition thanthe generic definition of “coupled” provided above. Such coupling may bemechanical, electrical, or fluidic.

The term “or,” as used herein, is used in its inclusive sense (and notin its exclusive sense) so that when used to connect a list of elements,the term “or” means one, some, or all of the elements in the list.Conjunctive language such as the phrase “at least one of X, Y, and Z,”unless specifically stated otherwise, is understood to convey that anelement may be either X, Y, Z; X and Y; X and Z; Y and Z; or X, Y, and Z(i.e., any combination of X, Y, and Z). Thus, such conjunctive languageis not generally intended to imply that certain embodiments require atleast one of X, at least one of Y, and at least one of Z to each bepresent, unless otherwise indicated.

References herein to the positions of elements (e.g., “top,” “bottom,”“above,” “below”) are merely used to describe the orientation of variouselements in the FIGURES. It should be noted that the orientation ofvarious elements may differ according to other exemplary embodiments,and that such variations are intended to be encompassed by the presentdisclosure.

The hardware and data processing components used to implement thevarious processes, operations, illustrative logics, logical blocks,modules and circuits described in connection with the embodimentsdisclosed herein may be implemented or performed with a general purposesingle- or multi-chip processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. A generalpurpose processor may be a microprocessor, or, any conventionalprocessor, controller, microcontroller, or state machine. A processoralso may be implemented as a combination of computing devices, such as acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. In some embodiments, particularprocesses and methods may be performed by circuitry that is specific toa given function. The memory (e.g., memory, memory unit, storage device)may include one or more devices (e.g., RAM, ROM, Flash memory, hard diskstorage) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent disclosure. The memory may be or include volatile memory ornon-volatile memory, and may include database components, object codecomponents, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present disclosure. According to anexemplary embodiment, the memory is communicably connected to theprocessor via a processing circuit and includes computer code forexecuting (e.g., by the processing circuit or the processor) the one ormore processes described herein.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, orother optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps, and decision steps.

It is important to note that the construction and arrangement of varioussystems (e.g., system 100, system 200, etc.) and methods as shown in thevarious exemplary embodiments is illustrative only. Additionally, anyelement disclosed in one embodiment may be incorporated or utilized withany other embodiment disclosed herein. Although only one example of anelement from one embodiment that can be incorporated or utilized inanother embodiment has been described above, it should be appreciatedthat other elements of the various embodiments may be incorporated orutilized with any of the other embodiments disclosed herein.

What is claimed is:
 1. A hose assembly for a hydraulic system, the hoseassembly comprising: a first hose configured to fluidly couple a pumpwith a hydraulic actuator using a first port, wherein the first hosecomprises a first electronic device configured to provide identificationinformation for the first hose; a second hose configured to fluidlycouple the hydraulic actuator with a hydraulic return component using asecond port, wherein the second hose comprises a second electronicdevice configured to provide identification information for the secondhose; and a controller configured to: receive a first connection signalusing the identification information for the first hose and a secondconnection signal using the identification information for the secondhose; determine that the first hose has fluidly coupled using the firstport based on the first connection signal; and determine that the secondhose has fluidly coupled using the second port based on the secondconnection signal.
 2. The hose assembly of claim 1, wherein thecontroller is further configured to: determine a connection fault basedon at least one of the first connection signal and the second connectionsignal; determine that the connection fault is based on at least one of:the first hose fluidly coupling the pump using the second port; or thesecond hose fluidly coupling the hydraulic return component using thefirst port; and adjust internal operation of the hydraulic manifold tofluidly couple the pump with the hydraulic actuator using the first hoseand to fluidly couple the hydraulic actuator with the hydraulic returncomponent using the second hose.
 3. The hose assembly of claim 1:further comprising a hydraulic manifold, the hydraulic manifoldcomprising the first port and the second port; or the hydraulic actuatorcomprising the first port and the second port; wherein the first port isconfigured to allow fluid to flow from the pump to the hydraulicactuator; and wherein the second port is configured to allow the fluidto flow from the hydraulic actuator to the hydraulic return component.4. The hose assembly of claim 3, further comprising: a first transmitterproximate to the first port, the first transmitter configured to:communicate with the first electronic device to receive theidentification information for the first hose; and provide the firstconnection signal based on the identification information for the firsthose, wherein the first connection signal comprises an indication thatthe first hose is connected to the first port; and a second transmitterproximate to the second port, the second transmitter configured to:communicate with the second electronic device to determine theidentification information for the second hose; and provide the secondconnection signal based on the identification information for the secondhose, wherein the second connection signal comprises an indication thatthe second hose is connected to the second port.
 5. The hose assembly ofclaim 4, wherein the first transmitter and the first electronic devicecommunicate via passive tag radio-frequency identification (RFID),active tag RFID, near-field communication (NFC), near-field magneticinduction (NFMI), Bluetooth, or Wi-Fi.
 6. The hose assembly of claim 5,wherein the first electronic device is a passive RFID tag and the firsttransmitter comprises an active RFID reader configured to read thepassive RFID tag to determine the identification information for thefirst hose.
 7. The hose assembly of claim 1, wherein the controller isfurther configured to provide a notification of the connection fault toa monitoring device of the hydraulic system.
 8. A method of determiningfaults in a hydraulic system, the method comprising: receiveidentification information and connection information for a first hosebased on a first receiver on the first hose, the first hose configuredto fluidly couple a pump with a hydraulic actuator using a first port;receive identification information and connection information for asecond hose based on a second receiver on the second hose, the secondhose configured to fluidly couple the hydraulic actuator with ahydraulic return component using a second port; determine a connectionfault based on at least one of the identification information andconnection information for the first hose and the identificationinformation and connection information for the second hose; and providea notification of the connection fault to a monitoring device of thehydraulic system.
 9. The method of claim 8, wherein receivingidentification information and connection information for the first hosecomprises: receiving identification information that identifies a type,a manufacture, a functionality, or a configuration of the first hose;and receiving connection information that identifies a port that thefirst hose uses to fluidly couple the pump.
 10. The method of claim 8,wherein providing the notification of the connection fault to themonitoring device comprises: displaying an alert on a user interfaceindicating that the connection fault has been detected; and providing aproposed solution to the user interface, the proposed solutioncomprising instructions to reconnect the first hose or the second hoseto another port or adjust internal operation of a hydraulic manifold.11. The method of claim 8, further comprising: determining that thefirst hose is fluidly coupling the pump using the second port and thatthe second hose is fluidly coupling the hydraulic return component usingthe first port; and adjusting internal operation of a hydraulic manifoldto fluidly couple the pump with the hydraulic actuator using the firsthose and to fluidly couple the hydraulic actuator with the hydraulicreturn component using the second hose.
 12. The method of claim 11,wherein: the hydraulic manifold comprises the first port and the secondport or the hydraulic actuator comprising the first port and the secondport; the first port is configured to allow fluid to flow from the pumpto the hydraulic actuator; and the second port is configured to allowthe fluid to flow from the hydraulic actuator to the hydraulic returncomponent.
 13. The method of claim 8, wherein receiving identificationinformation and connection information for the first hose comprisesreceiving identification information and connection information viapassive tag radio-frequency identification (RFID), active tag RFID,near-field communication (NFC), near-field magnetic induction (NFMI),Bluetooth, or Wi-Fi.
 14. The method of claim 13, wherein receivingidentification information and connection information for the first hosecomprises receiving receive identification information and connectioninformation via a passive RFID tag coupled to the first hose and anactive RFID reader proximate to the first port, the active RFID readerconfigured to read the passive RFID tag to determine the identificationinformation for the first hose.
 15. The method of claim 8, wherein:determining a connection fault based on at least one of theidentification information and connection information comprisesdetermining that the first hose has disconnected from the first port;and providing a notification of the connection fault comprises providingan indication of the first hose being disconnected from the first portto the monitoring device.
 16. A hose apparatus for a hydraulic system,the hose apparatus comprising: a first hose configured to fluidly couplea pump with a hydraulic actuator using a first port, wherein the firsthose comprises a first electronic device; and the first electronicdevice configured to: provide identification information for the firsthose to a transmitter, the transmitter configured to provide a firstconnection signal using the identification information for the firsthose, the first connection signal used to determine a connection faultbased on the first connection signal, wherein, upon the first hosefluidly coupling the pump using a different port, the hydraulic systemis automatically adjusted such that the first hose fluidly couples thepump with the hydraulic actuator using the different port.
 17. The hoseapparatus of claim 16, further comprising: a second hose configured tofluidly couple the hydraulic actuator with a hydraulic return componentusing a second port, wherein the second hose comprises a secondelectronic device configured to provide a second connection signal usingthe identification information for the second hose, the secondconnection signal used to determine the connection fault based on thesecond connection signal.
 18. The hose apparatus of claim 17, furthercomprising a controller configured to: determine that the connectionfault is based on at least one of: the first hose fluidly coupling thepump using the second port; or the second hose fluidly coupling thehydraulic return component using the first port; and adjust internaloperation of the hydraulic system to fluidly couple the pump with thehydraulic actuator using the first hose and to fluidly couple thehydraulic actuator with the hydraulic return component using the secondhose.
 19. The hose apparatus of claim 18: further comprising a hydraulicmanifold, the hydraulic manifold comprising the first port and thesecond port; or the hydraulic actuator comprising the first port and thesecond port; wherein the first port is configured to allow fluid to flowfrom the pump to the hydraulic actuator; and wherein the second port isconfigured to allow the fluid to flow from the hydraulic actuator to thehydraulic return component.
 20. The hose apparatus of claim 19, whereinthe transmitter and the first electronic device communicate via passivetag radio-frequency identification (RFID), active tag RFID, near-fieldcommunication (NFC), near-field magnetic induction (NFMI), Bluetooth, orWi-Fi.